Skip to content

Conversation

@florian-dacosta
Copy link

Presently, the module only works with the register payment button, which seems quite problematic, as it is normally not very used when the full accounting is done in Odoo.
Indeed, if you pay your invoice by wire transfer, the payment will come from your bank statement or from an account.payment.order for instance.

So the main change here is that the selected_for_payment is computed so it is removed when invoice is paid or in payment.

This PR includes other small improvement like :

possibility to mark the invoice as to pay from the form invoice view.
Make it possible to hide the field on tree view, since it is probably only for some users. Also, this allow to hide it on the customer invoice view, since it mainly concerns the supplier invoices.

Last thing, I think it is very weird to remove the selected_for_payment mark if one user click on the register payment button but does not proceed to the payment (cancel it).
I would remove the override of action_register_payment and only rely on the computed field to remove it...
Still I did not do it in this PR because I am not sure it is ok for everybody, and I do not really have a solution for the partial payment case.

An equivalent PR actually was already proposed/approved in v14, but was never merged see : #1317

FYI @aleuffre @renda-dev
@Kimkhoi3010 Can you re-do your review over here?
@sebalix @TDu @grindtildeath as reviewer of the migration PR it may be of your interest

…n payment

This way the module is usefull when the register payment wizard is not used. It is a case when you use payment orders or even if you reconcile your invoices from the bank statement for instance
Also add a button on form view to be able to mark the invoice as to pay when you are checking what it is exactly
@github-actions
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Aug 24, 2025
@florian-dacosta
Copy link
Author

@aleuffre @renda-dev @Kimkhoi3010 @sebalix @TDu @grindtildeath

I think it is an important improvement, a review would be appreciated.
@LESTRAT21

@github-actions github-actions bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Aug 31, 2025
@florian-dacosta
Copy link
Author

Copy link
Contributor

@aleuffre aleuffre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't really know the module, so I can't say functionally, but aside from a small note, Code Review LGTM.

style="background-color:grey"
/>
</button>
<xpath expr="//sheet/widget[5]" position="after">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question: would it be possible to choose a field in a more deterministic way?

e.g. //sheet/widget[@name='some_widget]or even//sheet/widget[last()]` ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants